Skip to content

fix: sync remove item may changed clone btree; (i+1) children has new… #61

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

zhangchuanqing5658
Copy link
Contributor

… cow, but do not copy; btree to btree generic

… cow, but do not copy; btree to btree generic

Signed-off-by: zhangchuanqing1 <[email protected]>
@RaduBerinde
Copy link

RaduBerinde commented Apr 19, 2025

I don't understand this fix. We are only copying the data inside mergeChild, why do we need mutableFor? In your comment in #58, t1 cannot modify any node shared between the trees (it will copy-on-write).

Can you produce an exact example that reproduces a problem? By the way, any fix should include a unit test that would have failed without the fix.

(posted the same in #58)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants